Attributes, Edge-Lists, & igraph, Oh My!
SNA Learning Lab 1
LASER Institute
June 23, 2021
PREPARE
Although social network analysis (SNA) and its educational antecedents date back to the early 1900s, public and scholarly interest in social network analysis did not really take off until the turn of the century (Carolan 2014). Applications of social network analysis has experienced exponential growth, and across a wide range of phenomena, as documented by a number of studies. One fun example of applied SNA is a study by Bioglio and Pensa (2018) at the University of Turn who used network measures of centrality to identify The Wizard of Oz as the most influential film of all time in a study published in the open access journal Applied Network Science.
While educational research lagging behind other fields in the application of SNA, an increase in the use of digital learning resources and data collected by these educational technologies, as well as improved access to training and tools for collecting and analyzing these data, has greatly facilitated the application of network analysis to teaching and learning.
SNA Module 1: The Social Network Perspective and MOOC-Eds is designed to prepare LASER Institute scholars for collecting, processing, and analyzing relational data and introduce a common application of SNA to help understand peer interaction in a discussion forum. Specifically, the two Learning Labs that make up this module address the following learning objectives:
Learning Lab 1: Attributes, Edge-Lists, & igraphs, Oh My! In our first lab, we prepare for analysis by gaining some context about our data; learning how to wrangle network data structures; and examining network descriptives such as network size, node degree and edge weights.
Learning Lab 2: Network Measures & Sociograms. For our second lab, we discuss the goals of network visualization and ways to explore relational data visually, including both static and dynamic network visualizations.
Review the Research
In Social Network Analysis and Education: Theory, Methods & Applications, Carolan (2014) notes that:
the social network perspective is one concerned with the structure of relations and the implication this structure has on individual or group behavior and attitudes
More specifically, Carolyn cites the following four features used by Freeman (2004) to define the social network perspective:
Social network analysis is motivated by a relational intuition based on ties connecting social actors.
It is firmly grounded in systematic empirical data.
It makes use of graphic imagery to represent actors and their relations with one another.
It relies on mathematical and/or computational models to succinctly represent the complexity of social life.
For Unit 1, our walkthrough will be guided by previous research and evaluation work conducted by the Friday Institute for Educational Innovation as part of the Massively Open Online Courses for Educators (MOOC-Ed) initiative. The study introduced next and the hands-on analysis with R in this walkthrough will help to illustrate these four defining features of the social network perspective.
A Social Network Perspective in MOOC-Eds
Kellogg, S., Booth, S., & Oliver, K. (2014). A social network perspective on peer supported learning in MOOCs for educators. International Review of Research in Open and Distributed Learning, 15(5), 263-289.
Research Context
In the spring of 2013, The Friday Institute launched the MOOC-Ed Initiative to explore the potential of delivering personalized, high-quality professional development to educators at scale (Kleiman et al., 2013). In collaboration with the Alliance for Excellent Education, the Friday Institute launched this initiative with a 6-week pilot course called Planning for the Digital Learning Transition in K-12 Schools (DLT 1), which was offered again in September 2013 (DLT 2). This course was designed to help school and district leaders plan and implement K-12 digital learning initiatives.
Academics, as well as pundits from traditional and new media, have raised a number of concerns about MOOCs, including the lack of instructional and social supports. Among the core design principles of MOOC-Eds are collaboration and peer-supported learning. It is an assumption of this study that challenges arising form this problem of scale can be addressed by leveraging these massive numbers to develop robust online learning communities.
This mixed-methods case study used both SNA and qualitative methods to better understand peer support in MOOC-Eds through an examination of the characteristics, mechanisms, and outcomes of peer networks. Findings from this study demonstrate that even with technology as basic as a discussion forum, MOOCs can be leveraged to foster these networks and facilitate peer-supported learning. Although this study was limited to two unique cases along the wide spectrum of MOOCs, the methods applied provide other researchers with an approach for better understanding the dynamic process of peer supported learning in MOOCs.
Data Sources
MOOC-Ed registration form. All participants completed a registration form for each MOOC-Ed course. The registration form consists of self-reported demographic data, including information related to their professional role and work setting, years of experience in education, and personal learning goals.
MOOC-Ed discussion forums. All peer interaction, including peer discussion, feedback, and reactions (e.g., likes), take place within the forum area of MOOC-Eds, which are powered by Vanilla Forums. Because of the specific focus on peer supported learning, postings to or from course facilitators and staff were removed from the data set. Finally, analyses described below exclude more passive forms of interactions (i.e., read and reaction logs), and include only postings among peers.
For our Unit 1 walkthrough, we’ll take a look at data from the original Digital Learning Transition in K-12 Schools (DLT 1) that was not included in this study to allow for comparisons to the findings in this study. For your independent analysis next week, you may want to consider working with the DLT 2 data to see if you can replicate some of the findings from this paper!
Note: In the data we’re using, instructors have not yet been removed and only direct replies to forum posts have been included, though “weaker” ties like reactions with emoticons and even views of posts were captured in this study.
Your Turn ⤵
Take a quick look at the Description of the Dataset section from the Massively Open Online Course for Educators (MOOC-Ed) network dataset BJET article and the accompanying data sets stored on Harvard Dataverse that we’ll be using for this walkthrough.
In the space below, type a brief response to the following questions:
What were some of the steps necessary to construct this dataset?
What two “node attributes” from the dataset that might be useful for predicting participants who may be more engaged or central to the network? Why did you select those two?
What else do you notice/wonder about this dataset?
Identify Questions
A Social Network Perspective on Peer Supported Learning in MOOC-Eds was framed by three primary research questions related to peer supported learning:
What are the patterns of peer interaction and the structure of peer networks that emerge over the course of a MOOC-Ed?
To what extent do participant and network attributes (e.g., homophily, reciprocity, transitivity) account for the structure of these networks?
To what extent do these networks result in the co-construction of new knowledge?
For our very first walkthrough, we are going to focus exclusively on RQ1 from the original study and our question of interest about our discussion network is:
To what extent, did educators engage with other participants in the discussion forums?
Who are the most central actors in our discussion network?
Your Turn ⤵
Based on what you know about networks and the context so far, what other research questions might ask we ask in this context that a social network perspective might be able to answer?
In the space below, type a brief response:
- YOUR RESPONSE HERE
We’ll revisit your response towards the end and provide an opportunity to refine your research question after you know the data a little better.
Load Libraries
As highlighted in Chapter 6 of Data Science in Education Using R (Estrellado et al. 2020):
Packages are shareable collections of R code that can contain functions, data, and/or documentation. Packages increase the functionality of R by providing access to additional functions to suit a variety of needs.
RStudio Tip: You can always check to see which packages have already been installed and loaded into RStudio Cloud by looking at the the Files, Plots, & Packages Pane in the lower right hand corner of RStudio as shown in the following screenshot:
You should see installed some familiar tidytext packages from our Getting Started assignment like {dplyr} and {readr} which we’ll be using again shortly. You should also see an important package call {igraph} that we will rely on heavily for our network analyses in this course.
If you are working in RStudio Desktop, or notice that the packages have not been installed and/or loaded, run the following install.packages() function code to install the {tidyverse} and {igraph} packages:
install.packages("tidyverse")
install.packages("igraph") Let’s go ahead and use the library() function for the {tidyverse} package and review which packages from the tidyverse collection of packages that this package also loads.
Click the green arrow to run the following code and load our {tidyverse} and {here} packages:
library(tidyverse)## ── Attaching packages ─────────────────────────────────────── tidyverse 1.3.1 ──## ✓ ggplot2 3.3.3 ✓ purrr 0.3.4
## ✓ tibble 3.1.2 ✓ dplyr 1.0.6
## ✓ tidyr 1.1.3 ✓ stringr 1.4.0
## ✓ readr 1.4.0 ✓ forcats 0.5.1## ── Conflicts ────────────────────────────────────────── tidyverse_conflicts() ──
## x dplyr::filter() masks stats::filter()
## x dplyr::lag() masks stats::lag()library(here)## here() starts at /cloud/project📦 The igraph Package
For our Unit 1 Walkthrough, we will rely heavily on the igraph network analysis package. The main goals of the igraph package and the collection of network analysis tools it contains are to provide a set of data types and functions for:
pain-free implementation of graph algorithms,
fast handling of large graphs, with millions of vertices (i.e., actors or nodes) and edges,
allowing rapid prototyping via high level languages like R.
Run the code chunk below to load the {igraph} library:
library(igraph)##
## Attaching package: 'igraph'## The following objects are masked from 'package:dplyr':
##
## as_data_frame, groups, union## The following objects are masked from 'package:purrr':
##
## compose, simplify## The following object is masked from 'package:tidyr':
##
## crossing## The following object is masked from 'package:tibble':
##
## as_data_frame## The following objects are masked from 'package:stats':
##
## decompose, spectrum## The following object is masked from 'package:base':
##
## unionYour Turn ⤵
Take a look at the messages from the output after loading the igraph library. What tidyverse packages share identically named functions with igraph?
Write your response in the space below.
- YOUR RESPONSE HERE
WRANGLE
In general, data wrangling involves some combination of cleaning, reshaping, transforming, and merging data Wickham and Grolemund (2016). The importance of data wrangling is difficult to overstate, as it involves the initial steps of going from the raw data to a dataset that can be explored and modeled Krumm, Means, and Bienkowski (2018).
For our data wrangling in Lab 1, we’re keeping it simple since working with network data is a bit of a departure from our working with rectangular data frames. Our primary goals for Unit 1 are learning how to:
Import Data. An obvious and also important first step, we need to “read” our data into R and learn about formatting for edge-lists and node attribute files.
Create a Network Object. Before performing network analyses, we’ll need to convert our data frames into special data format for working with relational data.
Simplify Network. Finally, we’ll learn about a handy
simplify()function in the {igraph} package for collapsing multiple ties between actors and removing “self-loops.”
Import Data
The Edge-List Format
To get started, we need to import, or “read,” our data into R. The function used to import your data will depend on the file format of the data you are trying to import, but R is pretty adept at working with many files types.
Take a look in the /data folder in your Files pane. You should see the following .csv files:
dlt1-edgelist.csvdlt1-nodes.csv
As its name implies, the first file dlt1-edgelist.csv is an edge-list that contains information about each tie, or relation between two actors in a network. In this context, a “tie” is a reply by one participant in the discussion forum to the post of another participant – or in some cases to their own post! These ties between a single actor are called “self-loops” and as we’ll see later in this section, igraph has a special function to remove these self loops from a sociogram, or network visualization.
The edge-list format is slightly different than other formats you have likely worked with before in that the values in the first two columns of each row represent a dyad, or tie between two nodes in a network. An edge-list can also contain other information regarding the strength, duration, or frequency of the relationship, sometime called “weight,” in addition to other “edge attributes.”
In addition to our Sender and Reciever dyad pairs, our DLT 1 dataset contains the following edge attributes:
Sender= Unique identifier of author of commentReceiver= Unique identifier of identified recipient of commentTimestamp= Time post or reply was postedParent= Primary category or topic of threadCategory= Subcategory or subtopic of threadThread_id= Unique identifier of a threadComment_id= Unique identifier of a comment\
Let’s use the read_csv() function from the {readr} package introduced in the Getting Started walkthrough to read in our edge-list and print the new ties data frame:
ties <- read_csv(here("data", "dlt1-edgelist.csv"),
col_types = cols(Sender = col_character(),
Receiver = col_character(),
`Category Text` = col_skip(),
`Comment ID` = col_character(),
`Discussion ID` = col_character()))
ties## # A tibble: 2,529 x 9
## Sender Receiver Timestamp `Discussion Tit… `Discussion Cat… `Parent Categor…
## <chr> <chr> <chr> <chr> <chr> <chr>
## 1 360 444 4/4/13 16… Most important … Group N Units 1-3 Discu…
## 2 356 444 4/4/13 18… Most important … Group D-L Units 1-3 Discu…
## 3 356 444 4/4/13 18… DLT Resources—C… Group D-L Units 1-3 Discu…
## 4 344 444 4/4/13 18… Most important … Group O-T Units 1-3 Discu…
## 5 392 444 4/4/13 19… Most important … Group U-Z Units 1-3 Discu…
## 6 219 444 4/4/13 19… Most important … Group M Units 1-3 Discu…
## 7 318 444 4/4/13 19… Most important … Group M Units 1-3 Discu…
## 8 4 444 4/4/13 19… Most important … Group N Units 1-3 Discu…
## 9 355 356 4/4/13 20… DLT Resources—C… Group D-L Units 1-3 Discu…
## 10 355 444 4/4/13 20… Most important … Group D-L Units 1-3 Discu…
## # … with 2,519 more rows, and 3 more variables: Discussion Identifier <chr>,
## # Comment ID <chr>, Discussion ID <chr>Note the addition of the col_types = argument for changing the column types to character strings since the numbers for those particular columns indicate actors (Sender and Reciever) and attributes (Comment_ID and Discussion_Id). We also skipped the Category Text since this was left blank for deidentification purposes.
RStudio Tip: Importing data and dealing with data types can be a bit tricky, especially for beginners. Fortunately, RStudio has an “Import Dataset” feature in the Environment Pane that can help you use the {readr} package and associated functions to greatly facilitate this process.
Your Turn ⤵
Consider the example pictured below of a discussion thread from the Planning for the Digital Learning Transition in K-12 Schools (DLT 1) where our data orginated. This thread was initiated by participant I, so the comments by J and N are considered to be directed at I. The comment of B, however, is a direct response to the comment by N as signaled by the use of the quote-feature as well as the explicit mentioning of N’s name within B’s comment.
Now answer the following questions as they relate to the DLT 1 edge-list we just read into R.
Which actors in this thread are the
Senderand theReciever? Which actor is both?How many dyads are in this thread? Which pairs of actors are dyads?
Sidebar: Unfortunately, these types of nuances in discussion forum data as illustrated by this simple example are rarely captured through automated approaches to constructing networks. Fortunately, the dataset you are working with was carefully reviewed to try and capture more accurately the intended recipients of each reply.
Node Attributes
The second file we’ll be using contains all the nodes or actors (i.e., participants who posted to the discussion forum) as well as some of their attributes such as gender and years of experience in education.
Carolyn (2013) notes that most social network analyses include variables that describe attributes of actors, ones that are either categorical (e.g., gender, ethnicity, etc.) or continuous in nature (e.g., test scores, number of times absent, etc.). These attributes that can be incorporated into a network graph or model, making it more informative and can aid in testing or generating hypotheses.
These attribute variables are typically included in a rectangular array, or dataframe, that mimics the actor-by-attribute that is the dominant convention in social science, i.e. rows represent cases, columns represent variables, and cells consist of values on those variables.
As an aside, Carolyn also refers to this historical preference by researchers for “actor-by-attribute” data, in the absence of relational data in which the actor has been removed their social context, as the “sociological meatgrinder” in action. Specifically, this historical approach assumes that the actor does not interact with anyone else in the study and that outcomes are solely dependent of the characteristics of the individual.
Regardless, let’s read in our node attribute file and take a look at the actors and their attributes included in our dataset:
actors <- read_csv(here("data", "dlt1-nodes.csv"),
col_types = cols(UID = col_character(),
Facilitator = col_character(),
expert = col_character(),
connect = col_character()))Your Turn ⤵
Use the code chunk below to take a look at the actors data frame:
actors## # A tibble: 445 x 13
## UID Facilitator role1 experience experience2 grades location region country
## <chr> <chr> <chr> <dbl> <chr> <chr> <chr> <chr> <chr>
## 1 1 0 libm… 1 6 to 10 secon… VA South US
## 2 2 0 clas… 1 6 to 10 secon… FL South US
## 3 3 0 dist… 2 11 to 20 gener… PA North… US
## 4 4 0 clas… 2 11 to 20 middle NC South US
## 5 5 0 othe… 3 20+ gener… AL South US
## 6 6 0 clas… 1 4 to 5 gener… AL South US
## 7 7 0 inst… 2 11 to 20 gener… SD Midwe… US
## 8 8 0 spec… 1 6 to 10 secon… BE Inter… BE
## 9 9 0 clas… 1 6 to 10 middle NC South US
## 10 10 0 scho… 2 11 to 20 middle NC South US
## # … with 435 more rows, and 4 more variables: group <chr>, gender <chr>,
## # expert <chr>, connect <chr>Match up the attributes included in the node file with the following codebook descriptors. The first one has been done as an example.
Facilitator= Identification of course facilitator (1 = instructor)- Dummy variable for whether participants listed networking/collaboration with others as one of their course goals on the registration form
- Identifier of “expert panelists” invited to course to share experience through recorded Q&A
- Identification of course facilitator (1 = instructor)
- Professional role (eg, teacher, librarian, administrator)
- Years of experience as an educator
- Works with elementary, middle, and/or high school students
- Initial assignment of discussion group
RStudio Tip: To highlight a variable as shown above, add a backtick ` punctuation mark immediately before and after the word or phrase.
Create Network Object
Before we can begin using many of the functions from the {igraph} package for summarizing and visualizing our DLT 1 network, we first need to convert the data frames that we imported into an igraph network object, or an igraph graph. 🤷
Convert to igraph Graph
To do that, we will use the graph_from_data_frame() function. Note that I included the eval=FALSE argument in the code block below to prevent this code from running when we knit our final document. Otherwise it will produce an error since we can’t include help documentation in our knitted HTML file.
Run the following code to take a look at the help documentation for this function:
?graph_from_data_frameYou probably saw that this particular function takes the following three arguments, two of which are data frames:
d describes the edges of the network. The first two columns are the IDs of the source and the target node for each edge, in our case the
SenderandRevieverof a discussion post – the order matters! The following columns are edge attributes such as weight, type, label, or anything else.vertices starts with a column of node IDs and any following columns are interpreted as node attributes.
directed determines whether or not to create a directed graph.
Run the following code to specify our ties data frame as the edges of our network, our actors data frame for the vertices of our network and their attributes, and indicate that this is indeed a directed network.
network <- graph_from_data_frame(d = ties,
vertices = actors,
directed = T)
network## IGRAPH 38684b5 DN-- 445 2529 --
## + attr: name (v/c), Facilitator (v/c), role1 (v/c), experience (v/n),
## | experience2 (v/c), grades (v/c), location (v/c), region (v/c),
## | country (v/c), group (v/c), gender (v/c), expert (v/c), connect
## | (v/c), Timestamp (e/c), Discussion Title (e/c), Discussion Category
## | (e/c), Parent Category (e/c), Discussion Identifier (e/c), Comment ID
## | (e/c), Discussion ID (e/c)
## + edges from 38684b5 (vertex names):
## [1] 360->444 356->444 356->444 344->444 392->444 219->444 318->444 4 ->444
## [9] 355->356 355->444 4 ->444 310->444 248->444 150->444 19 ->310 216->19
## [17] 19 ->444 19 ->4 217->310 385->444 217->444 393->444 217->19 256->219
## + ... omitted several edgesCarolyn (2013) reminds us that one of the simplest and often ignored structural property of a social network is its size and explains that:
size is simply a measure of the number of nodes in the network.
He notes that the size of a network plays an important role in determining what happens in the network. For example, in a classroom of 30 students, it is not hard to imagine that the pattern of who communicates with whom will look much different than if the network consisted of hundreds or even thousands of students like in a MOOC.
Your Turn ⤵
Take a look at the very first line of the output which contains some basic information about our network and answer the following questions:
How many nodes and edges are in our network? Is this consistent with the number of observations in our data frames? Hint: Check the Environment pane.
The “D” and the “N” indicate that this is a Directed network and has the Name vertex attributes set. Why do the two spaces that follow these letters have dashes? Hint: check the help files.
Which vertex attribute did igraph interpret as numeric?
Simplify Graph
As you saw from the network output, our dataset has 2529 edges or ties and just a quick scan of the edges in the network shows that edges like 356 -> 444 occur at least more than once. So we know that participant 356 has replied to participant 444 at least twice.
Fortunately, the {igraph} package has a simplify() function for collapsing multiple edges so they are not represented more than once when we want visually depict our network with a sociogram.
Let’s use that function to simplify our network and save it as a simple_network, or a simple graph, which contains no self-loops or duplicate edges and which by default the simplify() function removes:
simple_network <- simplify(network, remove.loops = TRUE)
simple_network## IGRAPH 01566c2 DN-- 445 1936 --
## + attr: name (v/c), Facilitator (v/c), role1 (v/c), experience (v/n),
## | experience2 (v/c), grades (v/c), location (v/c), region (v/c),
## | country (v/c), group (v/c), gender (v/c), expert (v/c), connect (v/c)
## + edges from 01566c2 (vertex names):
## [1] 1->2 1->7 1->22 1->30 1->36 1->41 1->49 1->50 1->68 1->88
## [11] 1->92 1->109 1->112 1->137 1->144 1->154 1->161 1->192 1->195 1->198
## [21] 1->221 1->444 1->445 2->36 2->67 2->104 2->177 2->223 3->2 3->7
## [31] 3->223 3->310 4->5 4->7 4->26 4->29 4->98 4->107 4->193 4->198
## [41] 4->207 4->308 4->444 5->8 5->12 5->21 5->24 5->67 5->107 5->444
## [51] 5->445 6->5 6->7 6->11 6->41 6->42 6->62 6->68 6->100 6->116
## + ... omitted several edgesNote that simplify() removes self-loops by default, this does not really need to be included. If you wanted to keep them, you would simply set this to FALSE.
Your Turn ⤵
Take a look at the output for our simple graph now and answer the following questions:
How many unique edges are in the network? Why do you think this is considerably less than our total edges?
Did we potentially lose any important or useful information by collapsing multiple edges into a single edge or by removing self-loops?
Add Edge Weights
We noted earlier that edges can also contain attributes such as strength, duration or frequency, sometime called “weight.” These weights can not only help us better understand the relationship between two actors, but also aid in visualization and modeling later on.
When we used the simplify() function earlier, it collapsed our duplicate edges but we lost some vital information as a result, namely the frequency of replies among pairs of educators in our discussion forum.
Fortunately, the simplify() function contains an argument that will allow us to count the number of ties between two actors, similar to how we might use the count() function in the {dplyr} package like so:
edge_weights <- count(ties, Sender, Receiver)
edge_weights## # A tibble: 1,978 x 3
## Sender Receiver n
## <chr> <chr> <int>
## 1 1 109 1
## 2 1 112 1
## 3 1 137 1
## 4 1 144 2
## 5 1 154 1
## 6 1 161 1
## 7 1 192 2
## 8 1 195 1
## 9 1 198 1
## 10 1 2 1
## # … with 1,968 more rowsIn this case, we see that participant 1 replied to participant 144 twice throughout the course.
To add weights to our simplified network, we first need to add a weight variable to the edges in our original network igraph object.
The {igraph} package has a unique syntax for working with attributes of network objects. To add a weight attribute to the E() edges in our network we’ll use the $ operator which can be used to create a new weight variable – or select a variable as we’ll see later on – and we’ll use the <- assignment operator to add an initial value of 1 for the weight of each edge.
Let’s put that all together and run the code to add a weight of 1 to each edge in our network
E(network)$weight <- 1 Now let’s take a look at our igraph network object again:
network## IGRAPH 38684b5 DNW- 445 2529 --
## + attr: name (v/c), Facilitator (v/c), role1 (v/c), experience (v/n),
## | experience2 (v/c), grades (v/c), location (v/c), region (v/c),
## | country (v/c), group (v/c), gender (v/c), expert (v/c), connect
## | (v/c), Timestamp (e/c), Discussion Title (e/c), Discussion Category
## | (e/c), Parent Category (e/c), Discussion Identifier (e/c), Comment ID
## | (e/c), Discussion ID (e/c), weight (e/n)
## + edges from 38684b5 (vertex names):
## [1] 360->444 356->444 356->444 344->444 392->444 219->444 318->444 4 ->444
## [9] 355->356 355->444 4 ->444 310->444 248->444 150->444 19 ->310 216->19
## [17] 19 ->444 19 ->4 217->310 385->444 217->444 393->444 217->19 256->219
## + ... omitted several edgesWe can see that our network is now weighted as indicated by the “W” and that our new weight attribute has been added.
We can now use the edge.attr.comb = argument to “sum” the weights for each occurrence of a pair of actors, so if 1 replied to participant 144 five times over the course of the MOOC-Ed, there would be a weight of 5 for that pair.
Run the code to simplify our weighted network:
weighted_network <- simplify(network,
edge.attr.comb = list(weight="sum")
)Let’s take a look at the output and ignore the error message for now:
weighted_network## IGRAPH 5e0b358 DNW- 445 1936 --
## + attr: name (v/c), Facilitator (v/c), role1 (v/c), experience (v/n),
## | experience2 (v/c), grades (v/c), location (v/c), region (v/c),
## | country (v/c), group (v/c), gender (v/c), expert (v/c), connect
## | (v/c), Timestamp (e/x), Discussion Title (e/x), Discussion Category
## | (e/x), Parent Category (e/x), Discussion Identifier (e/x), Comment ID
## | (e/x), Discussion ID (e/x), weight (e/n)
## + edges from 5e0b358 (vertex names):## Error in attrs[[i]]: subscript out of boundsIf you received an error message, you can ignore that for now. It will not impact our analysis.
Your Turn ⤵
Take a look at the output for our simple graph now and answer the following questions:
How does the number of total edges and unique edges this compare to the totals reported for the DLT 2 course in our guiding study?
- YOUR RESPONSE HERE
What might explain the differences?
- YOUR RESPONSE HERE
COMMUNICATE
In this learning lab, we focused on gaining some context about our data; learning how to wrangle network data structures; and examining basic but important network descriptives such as network size, node degree and edge weights.. Below, add a few notes in response to the following prompts.
One thing I took away from this learning lab:
- YOUR RESPONSE HERE
One thing I want to learn more about:
- YOUR RESPONSE HERE
Congratulations - you’ve completed the first network analysis learning lab! To complete your work, you can click the drop down arrow at the top of the file, then select “Knit top HTML.” This will create a report in your Files pane that serves as a record of your code and its output you can open or share.
Reach (Optional)
For this learning lab, your reach is to prepare a network graph object using either your own data or data from second MOOC-Ed course iteration of the The Digital Learning Transition in K-12 Schools. Note, this data is also included in your data folder but can be downloaded from Harvard Dataverse as well.
Please (optionally) start on this work right here, including reading data, preparing it, and then creating a faceted plot using data of your choosing. If you do this, re-knit your document when complete or at a stopping point so you have a record of your work!
ties_2 <- read_csv(here("data", "dlt2-edgelist.csv"))##
## ── Column specification ────────────────────────────────────────────────────────
## cols(
## Sender = col_double(),
## Reciever = col_double(),
## Timestamp = col_character(),
## Title = col_character(),
## Category = col_character(),
## Parent = col_character(),
## Description = col_character(),
## CommentID = col_double(),
## DiscussionID = col_double()
## )## Warning: 1 parsing failure.
## row col expected actual file
## 2584 DiscussionID a double #N/A '/cloud/project/data/dlt2-edgelist.csv'actors_2 <- read_csv(here("data", "dlt2-nodes.csv"))##
## ── Column specification ────────────────────────────────────────────────────────
## cols(
## uid = col_double(),
## facilitator = col_double(),
## role = col_character(),
## experience2 = col_double(),
## experience = col_double(),
## grades = col_character(),
## location = col_character(),
## region = col_character(),
## country = col_character(),
## group = col_character(),
## gender = col_character(),
## expert = col_double(),
## connect = col_double()
## )network_2 <- graph_from_data_frame(d = ties_2,
vertices = actors_2,
directed = T)
E(network_2)$weight <- 1
weighted_network_2 <- simplify(network_2,
edge.attr.comb = list(weight="sum")
)
weighted_network_2## IGRAPH 575316e DNW- 492 2062 --
## + attr: name (v/c), facilitator (v/n), role (v/c), experience2 (v/n),
## | experience (v/n), grades (v/c), location (v/c), region (v/c), country
## | (v/c), group (v/c), gender (v/c), expert (v/n), connect (v/n),
## | Timestamp (e/x), Title (e/x), Category (e/x), Parent (e/x),
## | Description (e/x), CommentID (e/x), DiscussionID (e/x), weight (e/n)
## + edges from 575316e (vertex names):## Error in attrs[[i]]: subscript out of boundsAnother option is to click “Tutorial” in the top right corner of your RStudio window and to begin one of the {learnr} tutorials. If you start one of these, take a note on this work here as a record of what you’ve began.